Skip to content

bump: torch/torchaudio from 2.8.0 to 2.10.0#1285

Open
Dinsmoor wants to merge 1 commit into
fishaudio:mainfrom
Dinsmoor:main
Open

bump: torch/torchaudio from 2.8.0 to 2.10.0#1285
Dinsmoor wants to merge 1 commit into
fishaudio:mainfrom
Dinsmoor:main

Conversation

@Dinsmoor

Copy link
Copy Markdown

Bump PyTorch to 2.10.0 which includes bundled Triton 3.6.0 with proper aarch64 support. This enables native compilation (COMPILE=1) on NVIDIA GB10/Blackwell (sm_121a) hardware, reducing inference time from ~4-5 minutes to ~13 seconds on a 10-second clip.

Is this PR adding new feature or fix a BUG?

Fix BUG.

Is this pull request related to any issue? If yes, please link the issue.

#1262

^ this guy, I had to do a hell of a workaround.

Other notes

A lot of work for a stupid dependency resolution.

Test with COMPILE=1 docker compose --profile server build --no-cache then run with COMPILE=1 docker compose --profile server up like normal, runs great on my dgx spark.

Bump PyTorch to 2.10.0 which includes bundled Triton 3.6.0 with proper
aarch64 support. This enables native compilation (COMPILE=1) on
NVIDIA GB10/Blackwell (sm_121a) hardware, reducing inference time
from ~4-5 minutes to ~13 seconds on a 10-second clip.
@PoTaTo-Mika

Copy link
Copy Markdown
Collaborator

This will cause an error produced by a depricated feature from torchaudio.
"set_audio_backend" is depricated after torchaudio 2.8.0.

@Dinsmoor

Dinsmoor commented May 17, 2026 via email

Copy link
Copy Markdown
Author

@github-actions

Copy link
Copy Markdown
Contributor

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions Bot added the stale label Jun 17, 2026
@Dinsmoor

Copy link
Copy Markdown
Author

The developers not being present doesn't make it stale.

@github-actions github-actions Bot removed the stale label Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants